Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: setting connectivity loop interval to 30 seconds #2878

Merged
merged 2 commits into from
Jul 9, 2024

Conversation

gabrielmer
Copy link
Contributor

Description

@alrevuelta noticed that peers get added to the a node very slowly.

We used to have ConnectivityLoopInterval set to 15 seconds, and changed it around half a year ago to 1 minute. At that time, the change also caused issues to QA because of slow times getting peers.

The idea is to eventually set the wait times between two connectivity loops depending on the amount of peers a node has. See #2877

In the meantime, I propose changing it to 30 seconds as some kind of middle ground between the 15 seconds and 1 minute alternatives: twice as long as 15 seconds but half as much as 1 minute :)

LMK if it makes sense or not, it should help us fill our peers faster in the meantime

Changes

  • changed ConnectivityLoopInterval to 30 seconds

Copy link
Contributor

@alrevuelta alrevuelta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm by now. at some point we may want to have a shorter loop when peer count is very low, and higher when close to peer limit.

Copy link

github-actions bot commented Jul 4, 2024

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:2878

Built from d995768

Copy link
Contributor

@SionoiS SionoiS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be fine to use 15s the only problem that could happen is if sharded peer management is enabled and dials don't finish before the loop start again (i'm guessing at worst some dials would fail because of the hard limit).

Copy link
Collaborator

@Ivansete-status Ivansete-status left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks! 💯

@gabrielmer gabrielmer merged commit d0980eb into master Jul 9, 2024
7 of 10 checks passed
@gabrielmer gabrielmer deleted the chore-decreasing-connectivity-loop-interval branch July 9, 2024 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants